ShareWay IP Gateway User's Guide

Troubleshooting

I want to set the target server to a particular server, but that server doesn't show up in ShareWay IP's list.

• Verify that the server is running.
• Verify that ShareWay IP's AppleTalk connection is configured properly.
• Verify that you can see the server using the Chooser on the ShareWay IP machine. If you can't, there is an AppleTalk connectivity problem between the server and ShareWay IP machines.
• Verify that you have selected the zone in which the server resides.

The status window does not display a section for selecting a server on AppleTalk.

• You are using ShareWay IP Personal; verify this through the About box. ShareWay IP Personal only works with Mac OS personal file sharing (on the same machine as ShareWay IP).

An error message indicates that ShareWay IP cannot run after the Start button is hit.

• You are trying to run ShareWay IP Personal on a machine with AppleShare file server installed. ShareWay IP Personal only works with Mac OS personal file sharing. An AppleShare file server requires ShareWay IP Standard.
• A duplicate serial number was discovered on the network. You need to either find and stop the copy of ShareWay IP with the duplicate serial number, or obtain an additional serial number from Open Door Networks.

On a client Macintosh, when I select AppleShare in the Chooser, there is no "Server IP Address..." button.

• The "Server IP Address..." button will only appear if you are running AppleShare Client 3.7 or later.

On a client machine, I enter the IP address of ShareWay IP, but I get an error.

• If ShareWay IP is on a different machine than the server, verify that you entered the IP address of the ShareWay IP machine, not the server. ShareWay IP's IP address is displayed in ShareWay IP's status window.
• Verify that there is TCP/IP connectivity between the client and ShareWay IP machines. Try pinging ShareWay IP from the client using a ping program.
• If there is a firewall between the client and ShareWay IP, or if DoorStop is running on the ShareWay machine, verify that it has made port 548 accessible.
• Verify that ShareWay IP is running and active.

I can't log on to a Gateway-targeted server using a custom authentication mechanism. It works if I use AppleTalk, but not if I use TCP/IP through ShareWay IP.

• AppleShare Client version 3.8 or later is needed for support of Custom User Authentication Methods (UAMs) over IP. In addition, a new UAM may also be required on the server. Contact your server manufacturer to see if a new UAM is available.

After ShareWay IP is started, the status window shows "IP Address: <not available>".

• The ShareWay IP machine's IP address is not available. Use the ShareWay IP machine's TCP/IP control panel to give that machine an IP Address.
• If TCP/IP is configured to use DHCP or MacIP, ShareWay IP may be obtaining the IP address dynamically from the DHCP or MacIP server. The status will update to show the IP address when it's obtained.
• If you are using PPP, ShareWay IP will only have a usable IP address if the PPP connection has been established.

When I try to connect to a server through the Gateway, I get the message, "This file server will not allow any additional users to log on. Try again later."

• There are too many users trying to connect through the Gateway to the target server. ShareWay IP Standard will handle up to 20 users simultaneously, while ShareWay IP Personal will handle up to 10 users.
• There are too many total users trying to connect to the file server itself.

When I try to start ShareWay IP I get an error message that port 548 is already in use.

• You are running AppleShare IP on the Gateway machine. AppleShare IP's functionality makes using ShareWay IP redundant.
• You are running more than one copy of the Gateway on the same machine, which is not supported.

ShareWay IP displays an incorrect host name, or just an IP address, in the AFP URL field.

• There is no host (DNS) name assigned to the ShareWay IP machine.
• When a host name was assigned to the ShareWay IP machine, a "reverse DNS lookup" or "PTR" record was not assigned, or was assigned incorrectly. Contact your network administrator if you wish ShareWay IP to display the correct host name in the AFP URL.

When I enter my serial number to convert my eval copy to a full working copy, ShareWay says it's a duplicate serial number.

• Someone else on your network has already used the serial number you are attempting to use. Each copy of ShareWay IP on a given network must have a unique serial number.

When I enter my serial number to convert my eval copy to a full working copy, ShareWay says the serial number is invalid.

• ShareWay IP 2.0 will not accept serial numbers from previous versions. Be sure you are using the ShareWay IP 2.0 serial number you were supplied.
• ShareWay IP Personal will not accept ShareWay IP Standard serial numbers, and vice versa.

I moved my full working copy of ShareWay IP to another machine (OR: I reinstalled my System software), and it's now behaving like an eval copy again.

The AFP server targeted by ShareWay IP is not visible in AFP Engage's "Browse AFP Servers" window.

• Be sure that the ShareWay IP machine is running Mac OS 8.5
• Be sure the SLP plug-in is enabled through the extensions manager
• Be sure you are running ShareWay IP 2.0 or later
• Double-check the name of the server in the File Sharing control panel on the server machine
• Consult the AFP Engage! Users' Guide for limitations with SLP

I am not sure if the background version of ShareWay IP is running on a particular machine.

• Run the foreground version of ShareWay IP on that machine. If the background version is running, the foreground version will indicate that fact.

I get an error saying that logging could not be enabled.

• Check to make sure that another application does not have the log file open, and that your disk is not full.

A user logs on to a ShareWay-targeted server, but does nothing and logs off some time later. The total bytes transfered for that user, as shown in the log file, seem much too high.

• The BYTES_SENT field in the log file includes all bytes sent over a session, not just bytes read from or written to files. Bytes sent as part of AFP's periodic housekeeping functions are also included.

Back to Table of Contents
Back to How ShareWay IP Works